Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1535

reference: 537-tree-1
name: 1535
tree-preservation-order: undefined
537-tpo-1
uprn: 10013671900
address-text: 16-20 Billett Avenue, Waterlooville;Land adjacent to 16 and, 16 Billett Avenue, Waterlooville
point: POINT (-1.023469 50.884324)
geometry: MULTIPOLYGON (((-1.023242 50.884300,-1.023252 50.884344,-1.023284 50.884385,-1.023333 50.884417,-1.023396 50.884438,-1.023466 50.884445,-1.023537 50.884439,-1.023601 50.884419,-1.023652 50.884388,-1.023685 50.884348,-1.023697 50.884303,-1.023687 50.884259,-1.023655 50.884219,-1.023606 50.884186,-1.023543 50.884165,-1.023472 50.884158,-1.023402 50.884164,-1.023338 50.884184,-1.023287 50.884215,-1.023254 50.884255,-1.023242 50.884300)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL